Skip to content

chore(main): release protoc-gen-elixir-grpc 0.4.3#54

Merged
yordis merged 2 commits into
mainfrom
release-please--branches--main--components--protoc-gen-elixir-grpc
Jul 26, 2026
Merged

chore(main): release protoc-gen-elixir-grpc 0.4.3#54
yordis merged 2 commits into
mainfrom
release-please--branches--main--components--protoc-gen-elixir-grpc

Conversation

@sht-bot

@sht-bot sht-bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

An automated release has been created for you.

0.4.3 (2026-06-25)

Bug Fixes

  • protoc-gen-elixir-grpc: Leading slash in generated file paths (#53) (ac4777a)

This PR was generated with Release Please. See documentation.

@sht-bot
chore(main): release protoc-gen-elixir-grpc 0.4.3
c5ba7b5 
Signed-off-by: Straw Hat Team Bot <61149376+sht-bot@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented Jun 25, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@yordis, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 42c6b91a-348b-4609-bda0-d574ed6df31e

📥 Commits

Reviewing files that changed from the base of the PR and between c5ba7b5 and 13beb5c.

📒 Files selected for processing (1)
  • .github/.release-please-manifest.json

Walkthrough

Bumped cmd/protoc-gen-elixir-grpc to 0.4.3 in the release manifest and added the corresponding v0.4.3 changelog entry describing the generated file-path slash fix.

Changes

Release metadata update

Layer / File(s) Summary
Version bump and changelog entry
.github/.release-please-manifest.json, cmd/protoc-gen-elixir-grpc/CHANGELOG.md		 cmd/protoc-gen-elixir-grpc is updated to 0.4.3, and the changelog adds the v0.4.3 bug-fix note for leading slashes in generated file paths.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

autorelease: tagged

Poem

🐰 I hop through manifests tonight,
and nudge the version up just right.
A carrot-note in changelog ink,
says paths won’t start with a slashy blink.
Hop-hop—release in sight!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the automated release of protoc-gen-elixir-grpc version 0.4.3.
Description check ✅ Passed The description is directly related to the release and includes the changelog entry for the 0.4.3 bug fix.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-please--branches--main--components--protoc-gen-elixir-grpc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@yordis
Merge remote-tracking branch 'origin/main' into release-please--branc…
13beb5c 
…hes--main--components--protoc-gen-elixir-grpc

Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>

# Conflicts:
#	.github/.release-please-manifest.json
@yordis
yordis merged commit 864c753 into main Jul 26, 2026
3 checks passed
@yordis
yordis deleted the release-please--branches--main--components--protoc-gen-elixir-grpc branch July 26, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@sht-bot @yordis